Columbia Kermit/kermit.zip/newsgroups/misc.19970104-19970326/[e-mail] _Mon Feb 17 06:06:00 1997.msg

Internet Message Format | 2020-01-01 | 7KB

Return-Path: <[e-mail]>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
    by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id GAA24842
    for <[e-mail]>; Mon, 17 Feb 1997 06:05:59 -0500 (EST)
Received: (from news@localhost)
    by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id GAA13376
    for kermit.misc@watsun; Mon, 17 Feb 1997 06:05:59 -0500 (EST)
Newsgroups: comp.protocols.kermit.misc
Path: news.columbia.edu!panix!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!news.maxwell.syr.edu!hunter.premier.net!uunet!in3.uu.net!204.74.114.90!news.genuity.net!news.lafn.org!lafn.org!lafn.org!aw585
From: [e-mail] (Dallas Legan)
Subject: Re: OS/2 Specific DOS and MS-DOS Kermit
X-Nntp-Posting-Host: lafn.org
Message-ID: <[e-mail]>
Sender: [e-mail]
Reply-To: [e-mail] (Dallas Legan)
Organization: The Los Angeles Free-Net
References: <1997Feb15.090805.155151@forest> <[e-mail]> <[e-mail]>
Date: Mon, 17 Feb 1997 10:06:42 GMT
Lines: 141
Xref: news.columbia.edu comp.protocols.kermit.misc:6604


(First, I want to thank the people who responded - no definite
answers, yet, but here's my feedback, maybe what I've found can
provide a new clue? - DEL)

In a previous article, [e-mail] (Paul Coen) says:

>In article <[e-mail]>, [e-mail] (Kees Hendrikse) writes:
>> In <[e-mail]> [e-mail] (Dallas Legan) writes:
>>
>>> When booting 'Specific DOS' versions from a bootable DOS disk,
>>> when I boot MS-DOS Kermit, it gives a message:
>>>
>>> ?Warning: unknown hardware for port. Using Bios as BIOS4.
>>>
>>> Is there some trick around this problem, or is it
>>> just a limitation of booting DOS from inside OS/2?
>>
>> Even if you boot a specific DOS from a floppy or a diskimage, you still
>> have to go through OS/2 layers to reach the hardware. Check the settings
>> of the program object and see if COM_DIRECT_ACCESS is enabled. This should
>> give Kermit access to the port you want. If not, try to use the port via
>> the bios: "set port bios 1".
>>

I tried the COM_DIRECT_ACCESS, but it didn't seem to do the trick.
I'll recheck, to make sure I didn't add any more complications.
Same with set port bios 1 (or rather 'bios 4')

>
>Actually, you shouldn't need to do that.  As long as MS-Kermit knows
>what irq & address to look for a com port as, it'll run without
>error messages without COM_DIRECT_ACCESS under OS/2.  I've done
>it on versions from OS/2 2.0 and above.

Maybe the IRQ is getting changed?

>
>Something else is wrong.  Something else could be using COM4, but
>that's unlikely because he didn't report getting an error message
>in a Presentation Manager window offering recovery choices.
>
>My guess is that Com4 (since there really isn't a standard for it)
>is set to something other than MS-Kermit might expect it to be,
>or else OS/2 can't see it at all due to the same problem (or a hardware
>conflict).
>

I read over the KERMIT.BWR MS-DOS Kermit documentation file as
carefully as possible about use under OS/2. (by the way, it is
version 3.0 if that matters any, with a cheap Zoom modem -
maybe it is one of the hardware brain dead ones contributing to the
problem.)
I did the examination with DOS DEBUG, and COM4 seemed to be where
it was supposed to be (hex 2e8).

>If the COM port works from OS/2 programs (C-Kermit for OS/2 should
>be able to use it if the operating system can see it), you need
>to do a "SET COM4" command (I *think* I'm remembering that
>correctly) and then give the information on where to find Com4.
>You can get the information from your CONFIG.SYS file, either
>in the line where COM.SYS is loaded, or, if you're using the
>replacement SIO drivers, whatever the name of the device driver
>is -- I'm drawing a blank.  Anyway, write down the irq and
>base address, and go back to MS-Kermit.

I went back and added to
DEVICE=C:\OS2\BOOT\COM.SYS
to make it:
DEVICE=C:\OS2\BOOT\COM.SYS (3,3F8,4) (4,2E8,3)

and even added the
DEVICE=C:\OS2\MDOS\COMDD.SYS
which supposedly some software needs
(I don't know if I put it in the right position, or
even if the location in CONFIG.SYS matters?)

and also put in the STARTUP.CMD
a line of
MODE COM4: 57600 N 8 1 RTS=HS OCTS=ON
similar to what was recommended in KERMIT.BWR

None of this seemed to help, but maybe I'm overlooking something?

>
>Type "set com4 ?" and it'll tell you what the next item it wants
>is -- type it in, insert a space, and hit "?" again.  I can never
>exactly remember the command syntax -- on the rare occasions I've
>had to do this I usually use this method for figuring it out.
>
>If the COM port isn't visible from OS/2, you're going to need
>to look up COM.SYS in the online help and find out the syntax
>for adding port definitions.  And you're going to need to know
>the irq and address for your COM4 (and Com3, for that matter).
>If this is a plug-and-pray device under Warp 4, you can do
                                      AAAAAAAAAA-- no, it's not
                                         it's 3.0

>"rmview /irq /io /so" at a command prompt to find out where
>it was actually put by the operating system so you can edit the
>config.sys file.
>
>Again, this error shouldn't be happening if everything is set up
>correctly.  Sorry for the number of "I can't quite remember . . ."

(That's OK - not only can I not remember, I never knew to begin with
  ;-)   )

>above, but some information is at my office, and not overly
>accessable at the moment.
>

This isn't as pressing as it was, because reading over the
documents more, I found settings to make
MS-DOS Kermit running in a fullscreen DOS VDM session
run a lot perkier then it originally was, and also not to
hang -
SET TERMINAL TIMESLICE-RELEASE DISABLE
and setting
HW_TIMER ON
this may not be perfect, but it's a lot better then previously.

Still, why not the Specific DOS?
(I like the COMMAND.COM that I'm using on it)
I found that commenting out all COM device drivers
in CONFIG.SYS - COM.SYS AND VCOM.SYS (and COMDD.SYS if that matters
any) enabled MS-DOS Kermit to run from a
Specific DOS session booted from a disk.
This seems extremely awkward, but maybe it provides someone
more knowledgable about OS/2 a clue as to what will work more
smoothly.  Somehow, I suspect maybe the VIO.SYS I've seen
mentioned might solve it, but I don't know.

Again, thanks for the consideration,
and sorry for any spelling, grammer, or netiquette violations!

Regards,
Dallas E. Legan
562.862.4854 ext. '*'
[e-mail]
[e-mail]